Skip to main content

This is a new service – your feedback will help us to improve it.

Your data has issues

There is a problem

  • document-url column must have valid URIs
Reference Name Developer agreement type Planning application Document URL Notes Organisation Entry date Start date End date
S106-00639 section-106 P22/00161/F

Invalid URI

2024-02-01 2024-02-01
S106-00522 section-106 P22/00340/F

Invalid URI

2022-11-22 2022-11-22
S106-00213 section-106 PT16/0982/F

Invalid URI

2017-02-13 2017-02-13
S106-00353 section-106 PT16/6924/O

Invalid URI

2018-07-12 2018-07-12
S106-00184 section-106 PK06/1169/R3O

Invalid URI

2007-07-06 2007-07-06
S106-00267 section-106 PT17/2444/O

Invalid URI

2018-01-29 2018-01-29
S106-00516 section-106 P21/00546/F

Invalid URI

2022-08-31 2022-08-31
S106-00422 section-106 P19/1166/F

Invalid URI

2019-09-23 2019-09-23
S106-00067 section-106 PT14/1517/F

Invalid URI

2015-03-11 2015-03-11
S106-00230 section-106 PK09/0314/RVC

Invalid URI

2010-06-11 2010-06-11
S106-00562 section-106 PT18/6450/O

Invalid URI

2022-11-03 2022-11-03
S106-00376 section-106 PK18/0692/F

Invalid URI

2018-10-23 2018-10-23
S106-00027 section-106 PK10/1057/F

Invalid URI

2014-12-18 2014-12-18
S106-00276 section-106 PK16/2577/O

Invalid URI

2017-07-17 2017-07-17
S106-00127 section-106 PT14/1886/O

Invalid URI

2016-02-02 2016-02-02
S106-00322 section-106 PT16/3565/O

Invalid URI

2018-04-17 2018-04-17
S106-00273 section-106 PT15/5319/O

Invalid URI

2017-08-31 2017-08-31
S106-00485 section-106 P19/2575/F

Invalid URI

2022-01-12 2022-01-12
S106-00130 section-106 PT15/3219/F

Invalid URI

2016-07-13 2016-07-13
S106-00413 section-106 PK18/0799/O

Invalid URI

2019-07-22 2019-07-22
S106-00536 section-106 PT18/6360/F

Invalid URI

2022-03-25 2022-03-25
S106-00436 section-106 PT18/0902/F

Invalid URI

2019-03-11 2019-03-11
S106-00064 section-106 PT14/0344/F

Invalid URI

2015-01-06 2015-01-06
S106-00654 section-106 P23/01258/O

Invalid URI

2024-06-12 2024-06-12
S106-00628 section-106 P23/00143/F

Invalid URI

2023-09-15 2023-09-15
S106-00207 section-106 PK16/5579/F

Invalid URI

2017-05-15 2017-05-15
S106-00256 section-106 PT17/4800/O

Invalid URI

2017-12-18 2017-12-18
S106-00648 section-106 P23/01832/O

Invalid URI

2024-06-11 2024-06-11
S106-00293 section-106 PT17/2401/F

Invalid URI

2018-02-15 2018-02-15
S106-00342 section-106 PT17/2240/F

Invalid URI

2018-06-28 2018-06-28
S106-00050 section-106 PT12/3707/O

Invalid URI

2014-05-29 2014-05-29
S106-00001 section-106 PK04/1965/O

Invalid URI

2013-06-12 2013-06-12
S106-00356 section-106 PT15/0510/F

Invalid URI

2016-03-03 2016-03-03
S106-00239 section-106 PT16/6941/F

Invalid URI

2017-11-02 2017-11-02
S106-00571 section-106 P19/16741/F

Invalid URI

2021-04-29 2021-04-29
S106-00093 section-106 PT05/0535/F

Invalid URI

2005-08-09 2005-08-09
S106-00525 section-106 P21/05366/F

Invalid URI

2021-11-09 2021-11-09
S106-00287 section-106 PK17/3702/F

Invalid URI

2018-04-25 2018-04-25
S106-00233 section-106 PT07/2478/O

Invalid URI

2016-12-05 2016-12-05
S106-00479 section-106 P19/13184/F

Invalid URI

2021-01-22 2021-01-22
S106-00333 section-106 PT16/4774/O

Invalid URI

2018-07-23 2018-07-23
S106-00456 section-106 PT16/6924/O

Invalid URI

2018-07-11 2018-07-11
S106-00018 section-106 PT10/3060/F

Invalid URI

2012-08-21 2012-08-21
S106-00279 section-106 PK17/2864/F

Invalid URI

2018-03-28 2018-03-28
S106-00373 section-106 PK18/1922/F

Invalid URI

2019-01-30 2019-01-30
S106-00519 section-106 P20/06928/O

Invalid URI

2022-05-18 2022-05-18
S106-00465 section-106 P19/1275/F

Invalid URI

2020-12-16 2020-12-16
S106-00224 section-106 PT16/3579/O

Invalid URI

2017-06-22 2017-06-22
S106-00419 section-106 PK17/0704/F

Invalid URI

2019-08-14 2019-08-14
S106-00439 section-106 P19/3976/F

Invalid URI

2020-01-06 2020-01-06

Showing rows 301 to 350 of 489

How to fix this issue

Your dataset is missing the document-url column.

The Developer agreement guidance explains how to fix the issue:

document-url

How to improve South Gloucestershire Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL